Skip to content

feat(use-case): Cursor agent hooks for local EverOS memory - #319

Closed
Ayush7614 wants to merge 1 commit into
EverMind-AI:mainfrom
Ayush7614:feat/use-case-cursor-agent-memory
Closed

feat(use-case): Cursor agent hooks for local EverOS memory#319
Ayush7614 wants to merge 1 commit into
EverMind-AI:mainfrom
Ayush7614:feat/use-case-cursor-agent-memory

Conversation

@Ayush7614

@Ayush7614 Ayush7614 commented Jun 30, 2026 •
edited
Loading

Copy link
Copy Markdown

Summary

  • Add use-cases/cursor-agent-memory/ — a minimal Cursor Agent hooks integration for the EverOS 1.0 local HTTP API.
  • sessionStart: search EverOS and inject recalled memory as additional_context.
  • stop: read the composer transcript and append the latest turn via POST /api/v1/memory/add.
  • sessionEnd: POST /api/v1/memory/flush to extract the session into Markdown-backed memory.
  • Includes stdlib-only hooklib/ helpers, install.sh, env.example, README, and 9 unit tests.

Closes #318.

Test plan

  • uv run pytest tests/unit/test_use_cases/ -q (9 passed)
  • make ci (lint + unit + integration + package)

Notes

  • Uses EverOS 1.0 routes (/api/v1/memory/*), not the legacy cloud plugin API.
  • Per-prompt recall is limited by Cursor hook capabilities today; recall runs at session start. Documented in the README.

@Ayush7614
feat(use-case): add Cursor agent hooks for local EverOS memory
c154873 
Introduce use-cases/cursor-agent-memory with sessionStart recall,
stop save, and sessionEnd flush hooks against the EverOS 1.0 HTTP API,
plus unit tests for the shared hooklib helpers.

Closes EverMind-AI#318.
@github-actions github-actions Bot mentioned this pull request Jun 30, 2026
Open
@gloryfromca gloryfromca mentioned this pull request Oct 13, 2026
Closed
3 tasks done
@gloryfromca

gloryfromca commented Oct 13, 2026

Copy link
Copy Markdown
Member

Closing this, with an apology for the 3.5 months of silence first — 975 lines, 9 passing unit tests and a green make ci, and nobody replied. That is on us, not on the contribution.

Four concrete reasons, in the order they matter:

1. Cursor is now covered by the official MCP server. everos-mcp connects Cursor (and Claude Code, Codex, Claude Desktop) with uvx everos-mcp, versioned and tested on its own release cycle — see docs/mcp.md. That is the path we point users at now, so this directory would be a second answer to the same question.

2. The API it targets has moved. This was written against EverOS 1.0 and /api/v1/memory/*; the repo is on 1.4.1 and /api/v2 is canonical, with /api/v1 kept only as a legacy compatibility alias. Merging it today would land a new example already pinned to the older prefix.

3. 18 files and a tests/unit/test_use_cases/ package is a maintained surface, not an example. It pins both EverOS routes and Cursor's hook schema, and neither is ours to keep stable. The former would drift on our releases; the latter on Cursor's.

4. Integrations live in a separate repository now. Both of the in-repo integrations that existed when you opened this have since moved out — see #416 (dsh) and #418 (langfuse). EverMind-AI/Plugins is where this belongs, and it would be genuinely welcome there — the hooks approach gives automatic capture on sessionStart / stop / sessionEnd, which MCP tools do not, since those fire only when the assistant decides to call them. That difference is real and worth having somewhere.

If you port it, updating the routes to /api/v2 is the only substantive change needed. Sorry again for the wait, and thank you for the work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

[Use Case]: Cursor agent hooks for local EverOS memory

2 participants

@Ayush7614 @gloryfromca